SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Go

Go static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your GO code

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        3. Using publicly writable directories is security-sensitive

           Security Hotspot
        4. Using clear-text protocols is security-sensitive

           Security Hotspot
        5. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        6. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        7. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        8. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        9. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        10. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        11. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        12. Formatting SQL queries is security-sensitive

           Security Hotspot
        13. Hard-coded credentials are security-sensitive

           Security Hotspot
        14. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Hard-coded credentials are security-sensitive

        responsibility - trustworthy
        security
        Security Hotspot
        • cwe

        Because it is easy to extract strings from an application source code or binary, credentials should not be hard-coded. This is particularly true for applications that are distributed or that are open-source.

        In the past, it has led to the following vulnerabilities:

        • CVE-2019-13466
        • CVE-2018-15389

        Credentials should be stored outside of the code in a configuration file, a database, or a management service for secrets.

        This rule flags instances of hard-coded credentials used in database and LDAP connections. It looks for hard-coded credentials in connection strings, and for variable names that match any of the patterns from the provided list.

        It’s recommended to customize the configuration of this rule with additional credential words such as "oauthToken", "secret", …​

        Ask Yourself Whether

        • Credentials allow access to a sensitive component like a database, a file storage, an API or a service.
        • Credentials are used in production environments.
        • Application re-distribution is required before updating the credentials.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Store the credentials in a configuration file that is not pushed to the code repository.
        • Store the credentials in a database.
        • Use your cloud provider’s service for managing secrets.
        • If a password has been disclosed through the source code: change it.

        Exceptions

        • The rule ignores string literals that are used directly in Regexp methods.

        Sensitive Code Example

        func connect()  {
          user := "root"
          password:= "supersecret" // Sensitive
        
          url := "login=" + user + "&passwd=" + password
        }
        

        Compliant Solution

        func connect()  {
          user := getEncryptedUser()
          password:= getEncryptedPass() // Compliant
        
          url := "login=" + user + "&passwd=" + password
        }
        

        See

        • OWASP - Top 10 2021 Category A7 - Identification and Authentication Failures
        • OWASP - Top 10 2017 Category A2 - Broken Authentication
        • CWE - CWE-798 - Use of Hard-coded Credentials
        • CWE - CWE-259 - Use of Hard-coded Password
        • Derived from FindSecBugs rule Hard Coded Password
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use